System and devices facilitating dynamic network link acceleration

ABSTRACT

A peer to peer dynamic network acceleration method and apparatus provide enhanced communications directly between two or more enhanced devices, such as enhanced clients. The enhanced clients may comprise a front-end, a back-end, or both. In general, the front-end and back-end of the enhanced clients work in concert to translate data into an enhanced protocol for communication between the enhanced clients. The enhanced protocol may provide acceleration, security, error correction, and other benefits. Data from various applications may be seamlessly translated between a first protocol and the enhanced protocol, such that the applications need not be modified to use the enhanced protocol. The enhanced clients may automatically detect one another to establish an enhanced communications channel automatically.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/023,460, filed Feb. 28, 2011, which is a continuation-in-part of U.S.patent application Ser. No. 12/584,938, filed Sep. 14, 2009, now U.S.Pat. No. 8,195,823, issued Jun. 5, 2012, which is a continuation-in-partof U.S. patent application Ser. No. 11/346,767, filed Feb. 3, 2006, nowU.S. Pat. No. 7,975,066, issued Jul. 5, 2011, which is a divisional ofU.S. patent application Ser. No. 09/835,876, filed Apr. 16, 2001, nowU.S. Pat. No. 7,127,518, which claims priority to U.S. ProvisionalPatent Application No. 60/197,490, filed Apr. 17, 2000.

FIELD OF THE INVENTION

The present invention relates, in general, to network performance and,more particularly, to software, systems and methods for implementingdynamic network acceleration functionality within a networkinfrastructure.

BACKGROUND OF THE INVENTION

Increasingly, business data processing systems, entertainment systems,and personal communications systems are implemented by computers acrossnetworks that are interconnected by internetworks (e.g., the Internet).The Internet is rapidly emerging as the preferred system fordistributing and exchanging data. Data exchanges support applicationsincluding electronic commerce, broadcast and multicast messaging,videoconferencing, gaming, and the like.

The Internet is a collection of disparate computers and networks coupledtogether by a web of interconnections using standardized communicationsprotocols. The Internet is characterized by its vast reach as a resultof its wide and increasing availability and easy access protocols.Unfortunately, the heterogeneous nature of the Internet makes itdifficult for the hardware and software that implement the Internet toadd functionality.

The Open System Interconnection (OSI) network model usefully describesnetworked data communication, such as the Internet, as a series oflogical layers or protocol layers. Each layer provides services to thelayer above it, and shields the layer above it from details of lowerlayers. Each layer is configured to communicate with other similar levellayers. In general, computers at network nodes (e.g., clients andservers) implement higher level processes including application layer,presentation layer, and session layer processes. Lower level processes,including network layer, data link layer and physical layer operate toplace data in a form suitable for communication across a rawcommunication channel or physical link. Between the higher and lowerlevel processes is a transport layer that typically executes on amachine at the network node, but is highly dependent on the lower levelprocesses.

While standards exist for these layers, application designers have ahigh level of control and can implement semantics and functionality atthe higher layers with a great deal of latitude. In contrast, lowerlayers are highly standardized. Implementing or modifying functionalityin a lower layer protocol is very difficult as such changes can affectalmost all users of the network. Devices such as routers that aretypically associated with infrastructure operate exclusively at thelower protocol layers making it difficult or impossible to implementfunctionality such as real-time processing, data compression, encryptionand error correction within a network infrastructure.

Although the term “Internet infrastructure” encompasses a variety ofhardware and software mechanisms, the term primarily refers to routers,router software, and physical links between these routers that functionto transport data packets from one network node to another.

Internet infrastructure components such as routers and switches are, bydesign, asynchronous. Also by design, it is difficult to accuratelypredict or control the route a particular packet will take through theInternet. This architecture is intended to make the Internet more robustin the event of failures, and to reduce the cost, complexity andmanagement concerns associated with infrastructure components. As aresult, however, a particular node or machine cannot predict thecapabilities of the downstream mechanisms that it must rely on todeliver a packet to its destination. A sending node cannot expect allmechanisms in the infrastructure to support the functions and/or syntaxnecessary to implement such functions as real time processing, datacompression, encryption, and error correction.

For example, it is difficult if not impossible to conduct synchronous ortime-aware operations over the Internet. Such operations include, forexample, real-time media delivery, access to financial markets,interactive events, and the like. While each IP packet includesinformation about the time it was sent, the time base is not synchronousbetween sender and receiver, making the time indication inaccurate.Packets are buffered at various locations through the Internetinfrastructure, and there is no accurate way to ascertain the actual ageor time of issue of the packet. Hence, critical packets may arrive toolate.

Data compression is a well-known technique to improve the efficiency ofdata transport over a communication link. Typically, data compression isperformed at nodes sending the data and decompression performed at anode receiving the data. Infrastructure components responsible forsending the information between the sending and receiving processes donot analyze whether effective compression has been performed, nor canthe infrastructure implement compression on its own. Where either thesending or receiving process is incapable of effective compression, thedata goes uncompressed. This creates undesirable burden that affects allusers. While modems connecting a user over a phone line often applycompression to that link, there is no analogous function within theInternet infrastructure itself. A need exists for Internetinfrastructure components that compress data between network nodes toimprove transport within the Internet.

Similarly, encryption and other data security techniques are well knowntechniques to ensure only authorized users can read data. Likecompression, however, encryption is typically performed by user-leveland application-level processes. If either sending or receiving processcannot perform compatible encryption, the data must be sent in the clearor by non-network processes. A need exists for Internet infrastructurecomponents that apply encryption or other security processestransparently to users.

As another example, forward error correction (FEC) is a known techniqueto reduced traffic volume, reduce latency, and/or increase data transferspeed over lossy connections. FEC adds redundant information, alsoreferred to as error correction code, to the original message, allowingthe receiver to retrieve the message even if it contains erroneous bits.FEC coding can enhances decoded bit error rate values three order ofmagnitude relative to systems not implementing any FEC techniques. Whenthe error can be detected and corrected at the receiving end, there isless need to resend data. FEC is extensively used in many digitalcommunication systems at some level and in mass storage technology tocompensate for media and storage system errors.

However, FEC is not used within the Internet infrastructure. This stemsin part from the additional complexity, cost and management tasks thatsuch capability would impose on the system hardware and software. FECrequires that the sender and receiver both implement compatible FECprocesses. Hence, most if not all infrastructure components would haveto be replaced or modified to implement FEC in an effective manner.Efforts to implement FEC between sending and receiving nodes areoutlined in IETF RFC 2733. This proposed standard applies to real timetransport protocol (RTP) communications between a client and server.This FEC method affects endpoints to a data transfer, but does notaffect servers and or other infrastructure components located betweenthe endpoints. Hence, a need exists for systems and methods thatimplement FEC within the Internet infrastructure to offer the benefitsof FEC technology seamlessly to network users.

In most cases these types of functionality are implemented in higherlevel processes (e.g., the OSI application layer, presentation layer,session layer and/or transport layer). However this requires thatsending and receiving nodes implement a common syntax. For example, bothsending and receiving nodes must implement complementaryencryption/decryption processes, however once this is ensured, thecommunication will be encrypted through out transport. In practice thereare multiple standards for real-time processing, encryption,compression, and error correction, and one or the other node may beunable to support the protocols of the other nodes. Hence, it isdesirable to implement such functionality is a manner that isindependent of the higher level processes so that otherwise incompatibleor incapable application-level processes can benefit.

In other cases, for example real time processing and error correction,it is desirable to have the functionality implemented within the networkinfrastructure, not only between the nodes. For example, implementingerror correction only between the sending and receiving nodes is only apartial solution, as the infrastructure components that operate at lowernetwork layers (e.g., transport, network, data link and/or physicallayer) cannot read error correction codes inserted at higher networklayers. As another example, traffic prioritization within the networkbenefits from knowledge of when packets were actually sent so that theycan be delivered in time for real-time processes.

A particular need exists in environments that involve multiple usersaccessing a network resource such as a web server. Web servers aretypically implemented with rich functionality and are often extensiblein that the functionality provided can be increased modularly to providegeneral-purpose and special-purpose functions. Examples includeinformation services, broadcast, multicast and videoconference services,as well as most electronic commerce (e-commerce) applications. In theseapplications it is important that functionality provided bynetwork-connected resources be provided in a dependable, timely andefficient manner.

Many e-commerce transactions are abandoned by the user because systemperformance degradations frustrate the purchaser before the transactionis consummated. While a transaction that is abandoned while a customeris merely browsing through a catalog may be tolerable, abandonment whenthe customer is just a few clicks away from a purchase is highlyundesirable. However, existing Internet transport protocols and systemsdo not allow the e-commerce site owner any ability to distinguishbetween the “just browsing” and the “about to buy” customers as thisinformation is represented at higher network layers that are notrecognized by the infrastructure components. In fact, the vagaries ofthe Internet may lead to the casual browser receiving a higher qualityof service while the about-to-buy customer becomes frustrated andabandons the transaction.

SUMMARY OF THE INVENTION

A peer to peer dynamic network acceleration method and apparatus aredisclosed herein. Peer to peer dynamic network acceleration provides anenhanced link between two client devices. It is noted that a clientdisclosed herein may also or alternatively connect to servers and othercomputing devices directly through an enhanced link. Traditionally,these devices communicate via a standard protocol or link. The enhancedlink allows data traffic to be accelerated (among other things) directlyto/from the clients. A standard client may be enhanced with a front-endand/or back-end mechanism to establish and communicate across theenhanced link. The front-end and back-end may translate between astandard protocol, such as one used by an application, and an enhancedprotocol. In this manner, the application need not be modified to takeadvantage of the enhanced link.

A peer to peer dynamic network acceleration apparatus may have variousembodiments. For example, in one embodiment, an enhanced clientcomputing device may be provided. The enhanced client computing devicemay comprise one or more processors configured to process one or moredata packets of a first protocol, at least one front-end, and at leastone back-end. The first protocol may be a standard protocol.

The front-end may be configured to receive the data packets of the firstprotocol from the processors, and to encode the data packets of thefirst protocol to generate one or more data packets of a secondprotocol. The front-end may be configured to request establishment of anenhanced link from a remote back-end prior to encoding the data packetsof the first type to generate one or more data packets of a secondprotocol.

The back-end may be configured to receive one or more incoming datapackets of the generated by a remote front-end from one or more originaldata packets, and to decode the incoming data packets to restore theoriginal data packets. The incoming data packets may be of the secondprotocol and the original data packets may be of the first protocol. Theback-end may be configured to receive a request to establish an enhancedlink from the remote front-end prior to decoding the incoming datapackets to restore the original data packets.

The front-end and the back-end may implement preselected compatiblesemantics to encode and decode data packets of the first and secondprotocols. At least one network interface configured to communicate aplurality of data packets of the second protocol between the enhancedclient computing device and one or more remote client computing devicesmay be provided as well. The front-end may be configured to transmit oneor more discovery messages via the network interface and to receiveresponses thereto to automatically discover remote back-ends. Likewise,the back-end may be configured to respond to one or more discoverymessages from the remote front-end via the network interface.

It is contemplated that the front-end may be configured to receive oneor more encoded data packets generated by a remote back-end from one ormore original data packets at the remote back-end, and to decode theencoded data packets to restore the original data packets. The encodeddata packets being of the second protocol and the original data packetsbeing of the first protocol.

In another exemplary embodiment, a peer to peer network accelerationsystem may be provided. The peer to peer network acceleration system maycomprise at least one first client computing device having one or morefirst applications configured to communicate via a standard protocol.The first client computing device may comprise a front-end configured toencode the first data packets according to an enhanced protocol, and torestore one or more original data packets from one or more encoded datapackets, the first data packets and the original data packets being ofthe standard protocol. It is noted that the front-end may be configuredto intercept data packets only from the first applications for encoding.

The front-end may be configured to transmit one or more discoverymessages and receive responses thereto to detect the back-end of thesecond client computing device. The front-end may automaticallyestablish the enhanced link with the back-end upon detecting theback-end by communicating at least one of the encoded data packets tothe back-end.

At least one second client computing device may be included in thesystem. The second client computing device may have one or more secondapplications that communicate via the standard protocol. The secondclient computing device may comprise a back-end configured to restoreone or more first original data packets from the encoded data packets,and to encode one or more second data packets according to the enhancedprotocol, the first original data packets and the second data packetsbeing of the standard protocol. The back-end may be configured torespond to one or more discovery messages to identify the back-end tothe front-end.

The first applications and the second applications may be collaborationsoftware stored on a tangible medium, such as project collaborationsoftware, groupware, instant messaging software, video conferencingsoftware, and audio conferencing software.

The system may also include at least one enhanced link between the firstclient computing device and the second client computing device. Theenhanced link may comprise the encoded data packets and the second datapackets after they have been encoded. It is noted that the first clientcomputing device may be configured to send a request to establish theenhanced link to the second client computing device. In addition oralternatively, the second client computing device may be configured torespond to a request to establish the enhanced link from the firstcomputing device.

Various methods for transferring data between client devices are alsodisclosed herein. In one exemplary embodiment, the method fortransferring data between client devices comprises running a firstclient application on a first client device (the client applicationconfigured to generate and receive one or more first data packets of astandard protocol), encoding the first data packets according to anenhanced protocol to generate one or more first encoded data packets fortransfer to a second client application on a second client device, andreceiving one or more second encoded data packets of the enhancedprotocol (the second encoded data packets comprising data from one ormore original data packets). It is contemplated that or more discoverymessages may be sent to detect the second client device. It is alsocontemplated that only the first data packets from the first applicationmay be encoded to generate the first encoded data packets. The originaldata packets may be restored from the second encoded data packets, andthe original data packets may be passed to the first client application.

It is noted that various hardware add-ons or software may be used tofacilitate the enhanced data transfer. For example, a communicationinterface of a hardware add-on may be connected to the first clientdevice, and the first encoded data packets may be transferred to thesecond client application via a network interface of the hardwareadd-on. Alternatively or in addition, machine readable code may bedownloaded and stored on a tangible medium accessible to the firstclient device. The encoding of the first packets may then occur byexecuting the machine readable code.

Further objects, features, and advantages of the present invention overthe prior art will become apparent from the detailed description of thedrawings which follows, when considered with the attached figures.

DESCRIPTION OF THE DRAWINGS

The components in the figures are not necessarily to scale, emphasisinstead being placed upon illustrating the principles of the invention.In the figures, like reference numerals designate corresponding partsthroughout the different views.

FIG. 1 illustrates a general distributed computing environment in whichthe present invention is implemented;

FIG. 2 illustrates in block-diagram form entity relationships in asystem in accordance with the present invention;

FIG. 3 illustrates a domain name system used in an implementation of thepresent invention;

FIG. 4 illustrates front-end components of FIG. 2 in greater detail;

FIG. 5 illustrates back-end components of FIG. 2 in greater detail;

FIG. 6 illustrates in flow-diagram form processes involved in anexemplary implementation of the present invention;

FIG. 7 illustrates a conceptual block diagram of particular componentsintroduced in FIG. 2 in greater detail;

FIG. 8 illustrates exemplary pre-processing processes;

FIG. 9 illustrates exemplary post-processing processes;

FIG. 10 illustrates a general distributed computing environment in whichthe present invention is implemented;

FIG. 11 illustrates in block-diagram form entity relationships in asystem in accordance with the present invention;

FIG. 12 illustrates in block-diagram form entity relationships in anoperating system in accordance with the present invention;

FIG. 13 illustrates a general distributed computing environment in whichthe present invention is implemented;

FIG. 14 illustrates in block-diagram form entity relationships in asystem in accordance with the present invention;

FIG. 15 illustrates in block-diagram form entity relationships in anoperating system in accordance with the present invention; and

FIG. 16 illustrates a general distributed computing environment in whichthe present invention is implemented.

DETAILED DESCRIPTION OF THE INVENTION

In the following description, numerous specific details are set forth inorder to provide a more thorough description of the present invention.It will be apparent, however, to one skilled in the art, that thepresent invention may be practiced without these specific details. Inother instances, well-known features have not been described in detailso as not to obscure the invention.

A first set of inventions relate to the improved functionality andmetrics available when cooperating front-end and back-end mechanisms,such as servers or other network devices, are used to transport datathrough the public network. This first class of inventions enable anenhanced link in which both ends can be synchronized and so easily knowwhen the other end performed specific operations such as datagramgeneration and transmission. This enables each side to take actionsbased on the knowledge that was previously only available to thetransmitting side. Other functionality includes compression of trafficbetween front-end and back-end mechanisms using public or proprietarydata compression that can be readily selected and optimized for theparticular content data currently being transported. Similarly,encryption/decryption can be employed between the front-end and back-endmechanisms for enhanced security without impacting either a web serveror a web client that are principles of the transaction. Forward errorcorrection can be used to reduce the quantity of traffic, improvelatency, and/or increase speed of the transport between front-end andback-end components.

A second set of inventions relates to performance and functionalityimprovements enabled by implementing the front-end and back-endmechanisms as dynamically re-configurable elements. This second class ofinventions enables multiple front-ends to connect with and servicemultiple back-ends and/or one or more web servers or web sites. Theseinventions also include the ability for one front-end to servicemultiple back-ends and by extension multiple web servers or web sites.Similarly, one front-end can service multiple web servers or contentproviders directly.

In one aspect, the present invention involves a system for multiplexingdata from a plurality of links or channels onto a shared bandwidthchannel. The plurality of links may be fixed-bandwidth links, or maythemselves be shared bandwidth links. The plurality of links maycomprise a homogenous user-level protocol, such as HTTP, or may comprisea variety of user level protocols such as HTTP, FTP, NNTP, SMTP and thelike. The plurality of links may similarly comprise homogenousnetwork-layer and/or physical layer protocols, or may comprise a variedset of network-layer and physical layer protocols.

The shared bandwidth channel allows a variety of services to beprovided. Some advantages are achieved simply by multiplexing multiplelinks onto a single channel. This combination enables the single channelto be persistent thereby avoiding overhead associated with setting up,maintaining and breaking down connections that would otherwise berequired of each the multiple links. The single shared channel can alsoinclude more information than the protocols of the plurality of linksallow such as time synchronization information and quality of serviceinformation.

In a particular embodiment, the shared bandwidth channel transportspackets that are composed by selecting data from the plurality of linksin an order and rate determined to provide differential levels ofservice between packets. The differential service levels may mean thatsome of the data are transported with lower latency and/or higherquality of service than other data. The criteria for providingdifferential levels of service are not limited, but in particularembodiments are based on content type, user identity, user history, andsession statistics.

The present invention is illustrated and described in terms of adistributed computing environment such as an enterprise computing systemusing public communication channels such as the Internet. However, animportant feature of the present invention is that it is readily scaledupwardly and downwardly to meet the needs of a particular application.Accordingly, unless specified to the contrary, the present invention isapplicable to significantly larger, more complex network environments,including wireless network environments, as well as small networkenvironments such as conventional LAN systems.

The present invention is particularly useful in applications where thereis a large amount of data communicated between web servers and webclients (i.e., browser software) or where timeliness (e.g., low latencytransport) is important. For example, real-time stock quotes,multi-player games, multi-tiered service to ASP (application serviceprovider) software distribution models benefit from the improvementsprovided by the present invention. Although the present invention willbe described in terms of particular applications, these examples areprovided to enhance understanding and are not a limitation of theessential teachings of the present invention.

For purposes of this document, a web server is a computer running serversoftware coupled to the World Wide Web (i.e., “the web”) that deliversor serves web pages. The web server may have a unique IP address and beconfigured to accept connections in order to service requests by sendingback responses. A web server differs from a proxy server or a gatewayserver in that a web server has resident a set of resources (i.e.,software programs, data storage capacity, and/or hardware) that enableit to execute programs to provide an extensible range of functionalitysuch as generating web pages, accessing remote network resources,analyzing contents of packets, reformatting request/response traffic andthe like using the resident resources. In contrast, a proxy simplyforwards request/response traffic on behalf of a client to resourcesthat reside elsewhere, or obtains resources from a local cache ifimplemented. A web server in accordance with the present invention mayreference external resources of the same or different type as theservices requested by a user, and reformat and augment what is providedby the external resources in its response to the user. Commerciallyavailable web server software includes Microsoft Internet InformationServer (IIS), Netscape Netsite, Apache, among others. Alternatively, aweb site may be implemented with custom or semi-custom software thatsupports HTTP traffic.

Though described herein with reference to a web server, it iscontemplated that various servers may utilize the systems and methodsdescribed herein. For example, email, database, file and other dataservers may use an enhanced link to communicate their respective data toother server, clients, or other computing devices.

FIG. 1 shows an exemplary computing environment 100 in which the presentinvention may be implemented. Environment 100 includes a plurality oflocal networks such as Ethernet network 102, FDDI network 103 and TokenRing network 104. Essentially, a number of computing devices and groupsof devices are interconnected through a network 101. For example, localnetworks 102, 103 and 104 are each coupled to network 101 throughrouters 109. LANs 102, 103 and 104 may be implemented using anyavailable topology and may implement one or more server technologiesincluding, for example UNIX, Novell, or Windows NT networks, orpeer-to-peer type network. Each network will include distributed storageimplemented in each device and typically includes some mass storagedevice coupled to or managed by a server computer. Network 101comprises, for example, a public network such as the Internet or anothernetwork mechanism such as a fiber channel fabric or conventional WANtechnologies.

Local networks 102, 103 and 104 include one or more network appliances107. One or more network appliances 107 may be configured as anapplication and/or file server. Each local network 102, 103 and 104 mayinclude a number of shared devices (not shown) such as printers, fileservers, mass storage and the like. Similarly, devices 111 may be sharedthrough network 101 to provide application and file services, directoryservices, printing, storage, and the like. Routers 109 provide aphysical connection between the various devices through network 101.Routers 109 may implement desired access and security protocols tomanage access through network 101.

Network appliances 107 may also couple to network 101 through publicswitched telephone network 108 using copper or wireless connectiontechnology. In a typical environment, an Internet service provider 106supports a connection to network 101 as well as PSTN 108 connections tonetwork appliances 107.

Network appliances 107 may be implemented as any kind of networkappliance having sufficient computational function to execute softwareneeded to establish and use a connection to network 101. Networkappliances 107 may comprise workstation and personal computer hardwareexecuting commercial operating systems such as UNIX variants, MicrosoftWindows, Macintosh OS, and the like. At the same time, some appliances107 comprise portable or handheld devices using wireless connectionsthrough a wireless access provider such as personal digital assistantsand cell phones executing operating system software such as PalmOS,WindowsCE, EPOCOS, and the like. Moreover, the present invention isreadily extended to network devices such as office equipment, vehicles,and personal communicators that make occasional connection throughnetwork 101.

Each of the devices shown in FIG. 1 may include memory, mass storage,and a degree of data processing capability (e.g. one or more processors)sufficient to manage their connection to network 101. The computerprogram devices in accordance with the present invention are implementedin the memory of the various devices shown in FIG. 1 and enabled by thedata processing capability of the devices shown in FIG. 1. In additionto local memory and storage associated with each device, it is oftendesirable to provide one or more locations of shared storage such asdisk farm (not shown) that provides mass storage capacity beyond what anindividual device can efficiently use and manage. Selected components ofthe present invention may be stored in or implemented in shared massstorage.

The present invention operates in a manner akin to a private network 200implemented within the Internet infrastructure as shown in FIG. 2.Private network 200 enhances communications between a client 205 and aweb site 210 by implementing any of a variety of processes that enhanceefficiency and/or functionality independently of client 205 and/orserver 210. These processes include time synchronization processes,quality of service management processes, compression processes, securityprocesses, and error correction processes.

In the specific examples herein client 205 comprises a network-enabledgraphical user interface such as a web browser. However, the presentinvention is readily extended to client software other than conventionalweb browser software. Any client application that can access a standardor proprietary user level protocol for network access is a suitableequivalent. Examples include client applications for file transferprotocol (FTP) services, voice over Internet protocol (VoIP) services,network news protocol (NNTP) services, multi-purpose internet mailextensions (MIME) services, post office protocol (POP) services, simplemail transfer protocol (SMTP) services, as well as Telnet services. Inaddition to network protocols, the client application may access anetwork application such as a database management system (DBMS) in whichcase the client application generates query language (e.g., structuredquery language or “SQL”) messages. In wireless appliances, a clientapplication may communicate via a wireless application protocol or thelike.

For convenience, the term “web site” is used interchangeably with “webserver” in the description herein although it should be understood thata web site comprises a collection of content, programs and processesimplemented on one or more web servers. A web site is owned by thecontent provider such as an e-commerce vendor whereas a web serverrefers to set of programs running on one or more machines coupled to anInternet node. The web site 210 may be hosted on the site owner's ownweb server, or hosted on a web server owned by a third party. A webhosting center is an entity that implements one or more web sites on oneor more web servers using shared hardware and software resources acrossthe multiple web sites. In a typical web infrastructure, there are manyweb browsers, each of which has a TCP connection to the web server inwhich a particular web site is implemented. The present invention addstwo components to the infrastructure: a front-end 201 and back-end 203.Front-end 201 and back-end 203 are coupled by an enhanced link 202 thatforms, in essence, a private network.

Front-end mechanism 201 serves as an access point for client-sidecommunications. In the process of translating a requested domain nameinto an IP address of a particular server hosting the requested domainname, mechanisms described in reference to FIG. 3 operate to select aparticular front-end mechanism 201. In effect, the domain is dynamicallyassigned to the selected front-end mechanism. More than one front-end201 may host a single domain. So long as a client 205 associates thedomain name with the IP address of the selected front-end 201, allclient requests to the domain will be routed to the selected front-end201.

Front-end mechanism 201 implements a set of processes in the dynamicallyassigned domain that implement a gateway that functions as a substitutefor the web server(s) implementing web site 210 (i.e., from theperspective of client 205, front-end 201 appears to be the web site210). Front-end 201 comprises, for example, a computer that sits “close”to clients 205. By “close”, it is meant that the average latencyassociated with a connection between a client 205 and a front-end 201 isless than the average latency associated with a connection between aclient 205 and a web site 210. Desirably, front-end computers have asfast a connection as possible to the clients 205. For example, thefastest available connection may be implemented in a point of presence(POP) of an Internet service provider (ISP) 106 used by a particularclient 205. However, the placement of the front-ends 201 can limit thenumber of browsers that can use them. Because of this, in someapplications it is more practical to place one front-end computer insuch a way that several POPs can connect to it. Greater distance betweenfront-end 201 and clients 205 may be desirable in some applications asthis distance will allow for selection amongst a greater numberfront-ends 201 and thereby provide significantly different routes to aparticular back-end 203. This may offer benefits when particular routesand/or front-ends become congested or otherwise unavailable.

The enhanced link 202 is implemented by cooperative actions of thefront-end 201 and back-end 203. The back-end 203 processes and directsdata communication to and from web site 210. In preferred embodiments,the enhanced link 202 communicates data packets using a secondary orenhanced communication protocol. The secondary or enhanced protocol maybe a proprietary or non-standard protocol (e.g., a protocol distinctfrom that ordinarily used by a network or computing device) thatprovides advantages, such as security, increased efficiency, improvedtransfer rates, etc. . . . , as compared to standard protocols, such asTCP. Though various enhanced protocols may be used, the enhancedprotocol is generally referred to herein as the Transport MorphingProtocol™ (Trademark of Circadence Corporation) or TMP™ (Trademark ofCircadence Corporation) because TMP exemplifies elements and advantagesdesirable in an enhanced protocol. TMP is implemented over the publicInternet infrastructure in the particular example. Hence, the presentinvention does not require heavy infrastructure investments andautomatically benefits from improvements implemented in the generalpurpose network 101. Unlike the general purpose Internet, front-end 201and back-end 203 are programmably assigned to serve accesses to aparticular web site 210 at any given time.

It is contemplated that any number of front-end and back-end mechanismsmay be implemented cooperatively to support the desired level of servicerequired by the web site owner. The present invention implements amany-to-many mapping of front-ends to back-ends. Because the front-endto back-end mappings can be dynamically changed, a fixed hardwareinfrastructure can be logically reconfigured to map more or fewerfront-ends to more or fewer back-ends and web sites or servers asneeded.

Front-end 201 together with back-end 203 function to reduce trafficacross the enhanced link 202 and to improve response time for selectedbrowsers. Traffic across the enhanced link 202 is reduced, for example,by compressing data. Compression can be implemented using any availablecompression mechanism and may operate on a packet-by-packet level or byassembling data from multiple packets to compress across a larger dataset. Although compression may be applied equally to all data, it isknown that some types of data do not benefit from compression. It isalso known that certain compression mechanisms and algorithms are bettersuited for particular types of data. Accordingly, the present inventioncontemplates the dynamic selection of a compression mechanism based onthe type of data being processed. For example, HTML data, which makes upa large proportion of web-based traffic, typically includes ASCII textwhich is known to compress well using, for example, compressed HTMLmechanisms. Encrypted data, however, often does not compress well.Accordingly, the present invention may be implemented to applycompressed HTML techniques to HTML packets while passing encryptedpackets (e.g., packets using a secure HTTP scheme) without attemptingencryption. So long as front-end 201 and back-end 203 share a commonsemantic for performing the compression/decompression processes, anyavailable algorithm may be implemented.

Encryption processes are largely analogous to compression processes inthat they may be implemented by a number of available cipher algorithmsand mechanisms including stream ciphers and block ciphers providingvarious levels of data security. It usually is not valuable to encryptdata that is already encrypted, hence it is contemplated that encryptionmay be selectively applied. Moreover, a vast majority of datatransferred in many applications does not require encryption at all. Theparticular encryption mechanism used by the front-end 201 and back-end203 can be selected based upon the type of data, or designated on afile-by-file basis by a manager of server 210, for example. Front-end201 and back-end 203 must share a common encryption/decryption semantic,however.

In one embodiment, front-end 201 and back-end 203 share operationalinformation such as time synchronization and quality of service metricswith each other. This information is readily communicated by speciallydesignated packets transmitted on enhanced link 202, and/or by includingthe information in one or more enhanced packets, such as TMP packets,that are used to exchange this operational information. Traffic acrossenhanced link 202 is preferably managed by selectively transmittingpackets at a rate determined to provide adequate quality of service andsuitable packet delivery time using this knowledge shared between thefront-end 201 and back-end 203. Optionally, this operational informationcan be shared with processes running on client 205 and/or server 210 aswell, although such sharing would require special configuration ofclient 205 and/or server 210 and is not required to achieve the benefitsof the present invention.

Traffic may be further reduced by using forward error correction (FEC)techniques to compensate for lossy connections. A variety of FECtechniques are known that add various amounts of overhead to thetraffic. The selection of a particular method depends on the quality ofservice (i.e., transit times and packet loss rate and/or bit error rate)of the communication channel being used. In one implementation, astatically defined FEC mechanism can be implemented between front-end201 and back-end 203 based on average or worst-case quality of service(QoS). However, because both front-end 201 and back-end 203 haveknowledge of the QoS metrics of each other and are time synchronized, itis contemplated that the FEC mechanisms can be adaptive to current QoSmetrics. For example, a data packets may be encoded with a 1-bit/byteerror correction code during times of high QoS, and dynamically changedto a 3-bit/byte or 4-bit/byte error correction (or higher) encoding whenQoS degrades. So long as front-end 201 and back-end 203 share a commonsemantic for handling the FEC processes, the actual implementation ofthose processes is very flexible and can be dynamically defined.

The blending of request datagrams results in fewer request:acknowledgepairs across the enhanced link 202 as compared to the number required tosend the packets individually between front-end 201 and back-end 203.This action reduces the overhead associated with transporting a givenamount of data, although conventional request:acknowledge traffic isstill performed on the links coupling the front-end 201 to client 205and back-end 203 to a web server. Moreover, resend traffic issignificantly reduced further reducing the traffic. Response time isfurther improved for select privileged users and for specially markedresources by determining the priority for each HTTP transmission.

In one embodiment, front-end 201 and back-end 203 are closely coupled tothe Internet backbone. This means they have high bandwidth connections,can expect fewer hops, and have more predictable packet transit timethan could be expected from a general-purpose connection. Although it ispreferable to have low latency connections between front-ends 201 andback-ends 203, a particular strength of the present invention is itsability to deal with latency by enabling efficient transport and trafficprioritization. Hence, in other embodiments front-end 201 and/orback-end 203 may be located farther from the Internet backbone andcloser to clients 205 and/or web servers 210. Such an implementationreduces the number of hops required to reach a front-end 201 whileincreasing the number of hops within the enhanced link 202 therebyyielding control over more of the transport path to the managementmechanisms of the present invention.

Clients 205 no longer conduct all data transactions directly with theweb server 210. Instead, clients 205 conduct some and preferably amajority of transactions with front-ends 201, which simulate thefunctions of web server 210. Client data is then sent, using enhancedlink 202, to the back-end 203 and then to the web server 210. Runningmultiple clients 205 over one large connection provides severaladvantages:

-   -   Since all client data is mixed, each client can be assigned a        priority. Higher priority clients, or clients requesting higher        priority data, can be given preferential access to network        resources so they receive access to the channel sooner while        ensuring low-priority clients receive sufficient service to meet        their needs.    -   The large connection between a front-end 201 and back-end 203        can be permanently maintained, shortening the many TCP/IP        connection sequences normally required for many clients        connecting and disconnecting.    -   Services such as encryption, compression, error correction and        time synchronization that may not be available or efficiently        implemented in particular clients 205 can be practically        implemented in enhanced link where the resources required to        provide these services are shared across multiple clients 205.

Using a proprietary protocol allows the use of more effective techniquesto improve data throughput and makes better use of existing bandwidthduring periods when the network is congested.

A particular advantage of the architecture shown in FIG. 2 is that it isreadily scaled. Any number of client machines 205 may be supported. In asimilar manner, a web site owner may choose to implement a site usingmultiple web servers 210 that are co-located or distributed throughoutnetwork 101. To avoid congestion, additional front-ends 201 may beimplemented or assigned to particular web sites. Each front-end 201 isdynamically re-configurable by updating address parameters to serveparticular web sites. Client traffic is dynamically directed toavailable front-ends 201 to provide load balancing. Hence, when qualityof service drops because of a large number of client accesses, anadditional front-end 201 can be assigned to the web site and subsequentclient requests directed to the newly assigned front-end 201 todistribute traffic across a broader base.

In the particular examples, this is implemented by a front-end managercomponent 207 that communicates with multiple front-ends 201 to provideadministrative and configuration information to front-ends 201. Eachfront-end 201 includes data structures for storing the configurationinformation, including information identifying the IP addresses of webservers 210 to which they are currently assigned. Other administrativeand configuration information stored in front-end 201 may includeinformation for prioritizing data from and to particular clients,quality of service information, and the like.

Similarly, additional back-ends 203 can be assigned to a web site tohandle increased traffic. Back-end manager component 209 couples to oneor more back-ends 203 to provide centralized administration andconfiguration service. Back-ends 203 include data structures to holdcurrent configuration state, quality of service information and thelike. In the particular examples a front-end manager 207 and a back-endmanager 209 serve multiple web sites 210 and so are able to manipulatethe number of front-ends and back-ends assigned to each web site 210 byupdating this configuration information. When the congestion for thesite subsides, the front-end 201 and back-end 203 can be reassigned toother, busier web sites. These and similar modifications are equivalentto the specific examples illustrated herein.

In the case of web-based environments, front-end 201 is implementedusing custom or off-the-shelf web server software. Front-end 201 isreadily extended to support other, non-web-based protocols, however, andmay support multiple protocols for varieties of client traffic.Front-end 201 processes the data traffic it receives, regardless of theprotocol of that traffic, to a form suitable for transport by enhancedlink 202 to a back-end 203. Hence, most of the functionality implementedby front-end 201 is independent of the protocol or format of the datareceived from a client 205. Hence, although the discussion of theexemplary embodiments herein relates primarily to front-end 201implemented as a web server, it should be noted that, unless specifiedto the contrary, web-based traffic management and protocols are merelyexamples and not a limitation of the present invention.

As shown in FIG. 2, in accordance with the present invention a web siteis implemented using an originating web server 210 operatingcooperatively with the web server of front-end 201. More generally, anynetwork service (e.g., FTP, VoIP, NNTP, MIME, SMTP, Telnet, DBMS) can beimplemented using a combination of an originating server workingcooperatively with a front-end 201 configured to provide a suitableinterface (e.g., FTP, VoIP, NNTP, MIME, SMTP, Telnet, DBMS, WAP) for thedesired service. In contrast to a simple front-end cache or proxysoftware, implementing a server in front-end 201 enables portions of theweb site (or other network service) to actually be implemented in andserved from both locations. The actual web pages or service beingdelivered comprises a composite of the portions generated at eachserver. Significantly, however, the web server in front-end 201 is closeto the browser in a client 205 whereas the originating web server isclose to all resources available at the web hosting center at which website 210 is implemented. In essence the web site 210 is implemented by atiered set of web servers comprising a front-end server 201 standing infront of an originating web server.

This difference enables the web site or other network service to beimplemented so as to take advantage of the unique topological positioneach entity has with respect to the client 205. By way of a particularexample, consider an environment in which the front-end server 201 islocated at the location of an ISP used by a particular set of clients205 and back-end 203 is closely coupled by a private channel to server210. In such an environment, clients 205 can access the front-end server205 without actually traversing the network 101, hence the need forencryption and error correction and time synchronization services arerelaxed with respect to the client-to-front-end link. In such cases theservices provided transparently by enhanced link 202 are substantially acomplete substitute for prior services implemented by modifying client205 and server 210 themselves.

In order for a client 205 to obtain service from a front-end 201, itmust first be directed to a front-end 201 that can provide the desiredservice. Preferably, client 205 does not need to be aware of thelocation of front-end 201, and initiates all transactions as if it werecontacting the originating server 210. FIG. 3 illustrates a domain nameserver (DNS) redirection mechanism that illustrates how a client 205 isconnected to a front-end 201. The DNS systems is defined in a variety ofInternet Engineering Task Force (IETF) documents such as RFC0883, RFC1034 and RFC 1035 which are incorporated by reference herein. In atypical environment, a client 205 executes a browser 301, TCP/IP stack303, and a resolver 305. For reasons of performance and packaging,browser 301, TCP/IP stack 303 and resolver 305 are often groupedtogether as routines within a single software product.

Browser 301 functions as a graphical user interface to implement userinput/output (I/O) through monitor 311 and associated keyboard, mouse,or other user input device (not shown). Browser 301 is usually used asan interface for web-based applications, but may also be used as aninterface for other applications such as email and network news, as wellas special-purpose applications such as database access, telephony, andthe like. Alternatively, a special-purpose user interface may besubstituted for the more general-purpose browser 301 to handle aparticular application.

TCP/IP stack 303 communicates with browser 301 to convert data betweenformats suitable for browser 301 and IP format suitable for Internettraffic. TCP/IP stack also implements a TCP protocol that managestransmission of packets between client 205 and an Internet serviceprovider (ISP) or equivalent access point. IP protocol requires thateach data packet include, among other things, an IP address identifyinga destination node. In current implementations the IP address comprisesa 32-bit value that identifies a particular Internet node. Non-IPnetworks have similar node addressing mechanisms. To provide a moreuser-friendly addressing system, the Internet implements a system ofdomain name servers that map alpha-numeric domain names to specific IPaddresses. This system enables a name space that is more consistentreference between nodes on the Internet and avoids the need for users toknow network identifiers, addresses, routes and similar information inorder to make a connection.

The domain name service is implemented as a distributed database managedby domain name servers (DNSs) 307 such as DNS_A, DNS_B and DNS_C shownin FIG. 3. Each DNS relies on <domain name:IP> address mapping datastored in master files scattered through the hosts that use the domainsystem. These master files are updated by local system administrators.Master files typically comprise text files that are read by a local nameserver, and hence become available through the name servers 307 to usersof the domain system.

The user programs (e.g., clients 205) access name servers throughstandard programs such as resolver 305. Resolver 305 includes an addressof a DNS 307 that serves as a primary name server. When presented with areference to a domain name (e.g., http://www.circadence.com), resolver305 sends a request to the primary DNS (e.g., DNS_A in FIG. 3). Theprimary DNS 307 returns either the IP address mapped to that domainname, a reference to another DNS 307 which has the mapping information(e.g., DNS_B in FIG. 3), or a partial IP address together with areference to another DNS that has more IP address information. Anynumber of DNS-to-DNS references may be required to completely determinethe IP address mapping.

In this manner, the resolver 305 becomes aware of the IP address mappingwhich is supplied to TCP/IP component 303. Client 205 may cache the IPaddress mapping for future use. TCP/IP component 303 uses the mapping tosupply the correct IP address in packets directed to a particular domainname so that reference to the DNS system need only occur once.

In accordance with the present invention, at least one DNS server 307 isowned and controlled by system components of the present invention. Whena user accesses a network resource (e.g., a web site), browser 301contacts the public DNS system to resolve the requested domain name intoits related IP address in a conventional manner. In a first embodiment,the public DNS performs a conventional DNS resolution directing thebrowser to an originating server 210 and server 210 performs aredirection of the browser to the system owned DNS server (i.e., DNC_Cin FIG. 3). In a second embodiment, domain:address mappings within theDNS system are modified such that resolution of the of the originatingserver's domain automatically return the address of the system-owned DNSserver (DNS_C). Once a browser is redirected to the system-owned DNSserver, it begins a process of further redirecting the browser 301 tothe best available front-end 201.

Unlike a conventional DNS server, however, the system-owned DNS_C inFIG. 3 receives domain:address mapping information from a redirectorcomponent 309. Redirector 309 is in communication with front-end manager207 and back-end manager 209 to obtain information on current front-endand back-end assignments to a particular server 210. A conventional DNSis intended to be updated infrequently by reference to its associatedmaster file. In contrast, the master file associated with DNS_C isdynamically updated by redirector 309 to reflect current assignment offront-end 201 and back-end 203. In operation, a reference to web server210 (e.g., http://www.circadence.com) may result in an IP addressreturned from DNS_C that points to any selected front-end 201 that iscurrently assigned to web site 210. Likewise, web site 210 may identifya currently assigned back-end 203 by direct or indirect reference toDNS_C.

Front-end 201 typically receives information directly from front-endmanager 207 about the address of currently assigned back-ends 203.Similarly, back-end 203 is aware of the address of a front-end 201associated with each data packet. Hence, reference to the domain systemis not required to map a front-end 201 to its appropriate back-end 203.

FIG. 4 illustrates principle functional components of an exemplaryfront-end 201 in greater detail. Primary functions of the front-end 201include translating standard packets, such as transmission controlprotocol (TCP) packets from client 205 into enhanced packets used in thesystem in accordance with the present invention. It is contemplated thatvarious functions described in reference to the specific examples may beimplemented using a variety of data structures and programs operating atany location in a distributed network. For example, a front-end 201 maybe operated on a network appliance 107 or server within a particularnetwork 102, 103, or 104 shown in FIG. 1.

TCP component 401 includes devices for implementing physical connectionlayer and Internet protocol (IP) layer functionality. Current IPstandards are described in IETF documents RFC0791, RFC0950, RFC0919,RFC0922, RFC792, RFC1112 that are incorporated by reference herein. Forease of description and understanding, these mechanisms are notdescribed in great detail herein. Where protocols other than TCP/IP areused to couple to a client 205, TCP component 401 is replaced oraugmented with an appropriate network protocol process.

TCP component 401 communicates TCP packets with one or more clients 205.Received packets are coupled to parser 402 where the Internet protocol(or equivalent) information is extracted. TCP is described in IETFRFC0793 which is incorporated herein by reference. Each TCP packetincludes header information that indicates addressing and controlvariables, and a payload portion that holds the user-level data beingtransported by the TCP packet. The user-level data in the payloadportion typically comprises a user-level network protocol datagram.

Parser 402 analyzes the payload portion of the TCP packet. In theexamples herein, HTTP is employed as the user-level protocol because ofits widespread use and the advantage that currently available browsersoftware is able to readily use the HTTP protocol. In this case, parser402 comprises an HTTP parser. More generally, parser 402 can beimplemented as any parser-type logic implemented in hardware or softwarefor interpreting the contents of the payload portion. Parser 402 mayimplement file transfer protocol (FTP), mail protocols such as simplemail transport protocol (SMTP), structured query language (SQL) and thelike. Any user-level protocol, including proprietary protocols, may beimplemented within the present invention using appropriate modificationof parser 402.

To improve performance, front-end 201 optionally includes a cachingmechanism 403. Cache 403 may be implemented as a passive cache thatstores frequently and/or recently accessed web pages or as an activecache that stores network resources that are anticipated to be accessed.In non-web applications, cache 403 may be used to store any form of datarepresenting database contents, files, program code, and otherinformation. Upon receipt of a TCP packet, HTTP parser 402 determines ifthe packet is making a request for data within cache 403. If the requestcan be satisfied from cache 403, the data is supplied directly withoutreference to web server 210 (i.e., a cache hit). Cache 403 implementsany of a range of management functions for maintaining fresh content.For example, cache 403 may invalidate portions of the cached contentafter an expiration period specified with the cached data or by websever 210. Also, cache 403 may proactively update the cache contentseven before a request is received for particularly important orfrequently used data from web server 210. Cache 403 evicts informationusing any desired algorithm such as least recently used, leastfrequently used, first in/first out, or random eviction. When therequested data is not within cache 403, a request is processed to webserver 210, and the returned data may be stored in cache 403.

Several types of packets will cause parser 404 to forward a requesttowards web server 210. For example, a request for data that is notwithin cache 403 (or if optional cache 403 is not implemented) willrequire a reference to web server 210. Some packets will comprise datathat must be supplied to web server 210 (e.g., customer creditinformation, form data and the like). In these instances, HTTP parser402 couples to data blender 404.

In accordance with the present invention, front-end 201 implementssecurity processes, compression processes, encryption processes, errorcorrection processes and the like to condition the received data forimproved transport performance and/or provide additional functionality.These processes may be implemented within pre-processing unit 408, oralternatively implemented within any of the functional components withinfront-end 201. Also, front-end 201 may implement a prioritizationprogram to identify packets that should be given higher priorityservice. A prioritization program requires only that front-end 201include a data structure associating particular clients 205 orparticular TCP packet types or contents with a prioritization value.Based on the prioritization value, parser 402 may selectively implementsuch features as caching, encryption, security, compression, errorcorrection and the like to improve performance and/or functionality. Theprioritization value is provided by the owners of web site 210, forexample, and may be dynamically altered, statically set, or updated fromtime to time to meet the needs of a particular application.

Blender 404 slices and/or coalesces the data portions of the receivedpackets into a more desirable “TMP data units” that are sized fortransport through the enhanced link 202. The data portion of TCP packetsmay range in size depending on client 205 and any intervening linkscoupling client 205 to TCP component 401. Moreover, where compression isapplied, the compressed data will vary in size depending on thecompressibility of the data. Data blender 404 receives information fromfront-end manager 217 that enables selection of a preferable TMP packetsize. Alternatively, a fixed TMP packet size can be set that yieldsdesirable performance across enhanced link 202. Data blender 404 alsomarks the TMP data units so that they can be re-assembled at thereceiving end. Data blender 404 may also serve as a buffer for storingpackets from all appliances 107 that are associated with front-end 201.In accordance with the present invention, data blender 404 may associatea prioritization value with each packet.

The enhanced link utilizes a TMP protocol, described in greater detailhereinbelow, to communicate TMP packets. Received TMP packets includesubpackets from multiple TCP connections. The data portions ofsubpackets are reassembled by reassemble mechanism 406 into a formsuitable for return to the requesting client 205. For example, in anHTTP environment reassemble mechanism 406 creates HTTP response payloadsakin to what would have been generated by an origin server 210.

Postprocessing mechanism 407 performs decompression, decryption, forwarderror correction and the like on packets received from a back-end 203.As described hereinafter with respect to FIG. 5, back-end 203 preferablyincludes pre-processing mechanisms 508 that are analogous topre-processing mechanisms 408. Hence, post-processing mechanisms 407restore the data to a form usable by a client 205 without additionalprocessing. Accordingly, client 205 need not implement any of thepre-processing or post processing functions while still realizing thebenefits of these processes.

FIG. 5 illustrates principle functional components of an exemplaryback-end 203 in greater detail. Primary functions of the back-end 203include translating transmission control protocol (TCP) packets from webserver 210 into TMP packets as well as translating TMP packets receivedfrom a front-end 201 into the one or more corresponding TCP packets tobe send to server 210. Further, back-end 203 is able to implementsimilar or complementary functionality to that of front-end 203. In thismanner, back-end 203 can operate as a web server to retrieve content andgenerate web pages, analyze and reformat web pages and components withinweb pages, and similar server functionality that would conventionally beimplemented in a server 210. In general, any functionality and behaviordescribed herein that can be implemented on server 210 and/or front-endserver 201 can also be implemented on back-end server 203.

TMP unit 505 receives TMP packets from enhanced link 202 and passes themto HTTP reassemble unit 507 where they are reassembled into thecorresponding TCP packets. Data filter 506 may implement otherfunctionality such as decompression, decryption, and the like to meetthe needs of a particular application. The reassembled data is forwardedto TCP component 501 for communication with web server 210.

TCP data generated by the web server process are transmitted to TCPcomponent 501 and forwarded to HTTP parse mechanism 502. Parser 502operates in a manner analogous to parser 402 shown in FIG. 5 to extractthe data portion from the received TCP packets. Pre-processing mechanism508 and post-processing mechanism 507 operate in an analogous fashion tocomponents 407 and 408 to perform compression, encryption, errorcorrection, and the like, and forward those packets to data blender 504.Data blender 504 operates in a manner akin to data blender 404 shown inFIG. 5 to buffer and prioritize packets in a manner that is efficientfor TMP transfer. Priority information is received by, for example,back-end manager 209 based upon criteria established by the web siteowner. TMP data is streamed into TMP unit 505 for communication onenhanced link 202.

In an exemplary implementation, illustrated in FIG. 6 and FIG. 7, a “TMPconnection” comprises a plurality of “TCP connection buffers”, logicallyarranged in multiple “rings”. Each TCP socket 701 maintained between thefront-end 201 and a client 205 corresponds to a TCP connection buffer702. Pre-processing 408 is performed on the TCP connection buffer datato provide, for example, data compression, encryption, and/or errorcorrection coding before the data is placed in the corresponding TCPconnection buffer 702.

When a TCP connection buffer 702 is created, it is assigned a priority.For purposes of the present invention, any algorithm or criteria may beused to assign a priority. Each priority ring is associated with anumber of TCP connection buffers having similar priority. In a specificexample, five priority levels are defined corresponding to five priorityrings. Each priority ring is characterized by the number of connectionbuffers it holds (nSockets), the number of connection buffers it holdsthat have data waiting to be sent (nReady) and the total number of bytesof data in all the connection buffers that it holds (nBytes).

A TCP connection buffer 702 is created and placing one or morepreprocessed packets from a TCP socket 701 within the TCP connectionbuffer 702. A TCP connection buffer 702 is sized to hold a plurality ofTCP packets and each TCP connection buffer 702 is associated with apriority value. The priority value is assigned when TCP connectionbuffer 702 is first created and may be dynamically changed in operation.

When sending data, blender 404 performs a series of processes outlinedin FIG. 6 that access data from the TCP connection buffers 702 to formTMP data units 705 that are transmitted. The processes performed byblender 404 include:

In step 602, determine the number of bytes available to be sent fromeach ring (nBytes), and the number of TCP connections that are ready tosend (nReady)

In step 603, determine how many bytes should be sent from each ring.This is based on a weight parameter for each priority. The weight can bethought of as the number of bytes that should be sent at each prioritythis time through the loop.

The nSend value computed in the previous step 603 reflects the weightedproportion that each ring will have in a blended TMP packet, but thevalues of nSend do not reflect how many bytes need to be selected toactually empty most or all of the data waiting to be sent a singleround. To do this, the nSend value is normalized to the ring having themost data waiting (e.g., nBytes=nSendNorm) in step 604. This involves acalculation of a factor: S=nBytes/(Weight*nReady) for the ring with thegreatest nReady. Then, for each ring, calculate nReady*S*Weight to getthe normalized value (nSendNorm) for each priority ring.

In step 605, sub-packets are sent from the different rings. This isdone, for example, by taking a sub-packet from the highest priority ringand adding it to a TMP packet, then adding a sub-packet from each of thetop two queues, then the top three, and so on. A variety of algorithmsmay be used to select particular sub-packets from the different rings toimplement a desired level of fairness, prioritization, and quality ofservice.

Referring to step 606, within each ring, sub-packets are added roundrobin. When a sub-packet is added from a TCP connection buffer the ringis rotated so the next sub-packet the ring adds will come from adifferent TCP connection buffer. Each sub-packet can be up to 512 bytesin a particular example. If the connection buffer has less than 512bytes waiting, the data available is added to the TMP packet.

In step 607, when a full TMP packet (roughly 1.5 kB in a particularexample) is built, it is sent. This can have three or more sub packets,depending on their size. The TMP packet will also be sent when there isno more data ready.

TMP unit 405 (shown in FIG. 4) and TMP unit 505 (shown in FIG. 5)implement the TMP protocol that communicates packets between front-end201 and back-end 203. The protocol is rides on top of universal datagramprotocol (UDP) in that network devices that handle TMP packets treatthem as UDP packets. However, TMP packets differ from standard UDPpackets in that they have additional unique header data defining aunique set of messages, outlined below, to support the TMPfunctionality. Also, the manner in which TMP packets are transferredonto the physical communication channel, referred to as the protocolbehavior, differs significantly from TCP.

TMP packets have a header that contains packet control information. SomeTMP packets also carry extra information in a data or payload portion.The packet control information includes, for example:

-   -   A connection number (that identifies the connection to which it        belongs)    -   A checksum for data integrity    -   A set of flags (which may be used or remain unused) for a        variety of purposes    -   A message type identifier    -   The confirmed message type

The rest of the packet header contains information or data which candiffer between packets, depending on the message type.

A short list of messages that can be sent by the TMP protocol includes:data, acknowledgments, connection requests and replies, timesynchronization requests and replies, resent data, control messages, QoSmessages, status requests and replies, suspend messages, and alerts.Packet header content which is specific to the message type is asfollows.

-   -   Acknowledgment        -   The last sequential confirmed sequence message        -   The confirmed message sequence number    -   Time Synchronization Request        -   Requester time index    -   Time Synchronization Reply        -   The time that the request was received        -   The time that the reply was sent        -   Requester time index    -   Connection Request        -   The connections index (zero for a new connection)        -   Requested receiving port        -   An additional set of flags (which may be used or unused) for            a variety of purposes    -   Connection Reply        -   The replier's base time        -   A time offset from the point of receiving the request in            milliseconds        -   The connections index (zero for a new connection)        -   An additional set of flags (which may be used or unused) for            a variety of purposes    -   Data        -   Data sequence number        -   Time that the message was sent

The rest of the packet comprises the packet body or payload portion.Alert and Acknowledge packets do not have bodies. All other packetscontain bodies that carry additional information appropriate to themessage itself (for example, a data packet will send the data itself).

It is important to note that alerts and QoS information are built intothe protocol and do not need to be passed as data packets. Since thesetypes of information are not built into TCP they would need to be sentas data, which might affect the application using the protocol. Thismeans that the receiving end needs to process the packet only once todraw out the information it requires. In contrast, when QoS informationis sent as a data packet in TCP, the receiving end has to process thepacket as a data packet simply to get to the information that allows thealert or QoS information to be processed, which means that TCP mustdouble the amount of processing for alerts and QoS information.

Of particular interest in the present invention, the exchange of timesynchronization information 707 enables front-end 201 and back-end 203to have a common time base and ascertain the time of issue of anyreceived packet. While the current implementation does not include basetime or time index data in the header of data packets, this informationcan readily be included in all message types, a subset of message types,and/or in a special message type defined for real-time data transport.In this manner, the recipient of a TMP packet knows with a high level ofcertainty when a received packet was transmitted, something thatexisting Internet protocols do not provide. In the case of TMP packetsfrom a back-end 203 to a front-end 201, the information can be used bythe front-end 201 as a factor in ordering responses to clients 205. Inthe case of TMP packets from a back-end 203 to a front-end 201, theinformation can be used by the front-end 203 as a factor in orderingresponses to clients 205.

Rather than synchronizing clocks the front-end 201 and back-end 203(i.e., absolute time synchronization), the time synchronizationinformation 707 may indicate a differential between the clocks of thetwo machines (i.e., relative time synchronization). Relative timesynchronization can be used substantially equivalently to informationthat would allow actual synchronization of the clocks. Accordingly,“time synchronization” and “time synchronized” refer inclusively to bothabsolute and relative time synchronization methods.

The time synchronization information 707 augments or replaces the “timeto live” feature of conventional IP packets. Each IP packet specifies atime to live value that must be decremented by each router or devicethat handles the packet. As the time value can only be incremented inone-second units, the value becomes a hop count rather than an actualtiming function. When a packet's time to live value is decremented tozero, it is discarded and must be retransmitted. In accordance with thepresent invention, the time to live value for TMP packets can be usedmore meaningfully as the recipient knows when the packet was actuallysent and can set or reset the time to live value to a meaningful valuewhen the packet leaves a front-end 201 or back-end 203.

As in all protocols, the messages in TMP have an order in which they aresent as well as particular defined situations in which they are sent. Atypical TMP session might begin with a connection request. Forreference, the end point that sends the connection request will bereferred to as the front-end, and the receiver of the request will bereferred to as the back-end, although the TMP protocol operatesbi-directionally between front-ends and back-ends. The front-end 201sends a connection request to the back-end 203, and the back-end 203sends a connection reply back to the front-end 201. This reply will beeither positive (connection accepted), or negative (connection refused).If the reply is positive, then the connection is established and thefront-end and back-end can begin to exchange data.

TMP is a TCP-like protocol adapted to improve performance for multipleconnections operating over a single pipe. The enhanced link inaccordance with the present invention provides a stable connectionbetween two processes for high-speed, reliable, adaptable communication.TMP is not merely a substitute for the standard TCP environment. TMP isdesigned to perform particularly well in heterogeneous networkenvironments such as the Internet. TMP connections are made less oftenthan TCP connections. Once a TMP connection is made, it remains upunless there is some kind of direct intervention by an administrator orthere is some form of connection-breaking network error. This reducesoverhead associated with setting up, maintaining and tearing downconnections normally associated with TCP.

Another feature of TMP is its ability to channel numerous TCPconnections through a single enhanced link 202. The environment in whichTMP resides allows multiple TCP connections to occur at one end of thesystem. These TCP connections are then mapped to a single TMPconnection. The TMP connection is then broken down at the other end ofthe enhanced link 202 in order to traffic the TCP connections to theirappropriate destinations. TMP includes mechanisms to ensure that eachTMP connection gets enough of the available bandwidth to accommodate themultiple TCP connections that it is carrying.

Another advantage of TMP as compared to traditional protocols is theamount of information about the quality of the connection that a TMPconnection conveys from one end to the other of a enhanced link 202. Asoften happens in a network environment, each end has a great deal ofinformation about the characteristics of the connection in onedirection, but not the other. QoS information 708 is exchanged betweenfront-end 201 and back-end 203 in accordance with the present invention.By knowing about the connection as a whole, TMP can better takeadvantage of the available bandwidth.

A QoS message is sent alone or may be piggybacked on a data packet. Itsends information regarding the connection from one end of theconnection to the other. Both front-end 201 and back-end 203 send QoSmessages. The information in a QoS message is the most up to date thatthe sending end has. That means that if a QoS message is to be resent,the QoS information is updated before it is resent. A QoS message isidentified by the message type flag QoS. In a particular implementation,a QoS message contains:

-   -   16 Bits—Average round trip time (RTT). This indicates the        average round trip time as calculated by this end of the system        over the last time interval, measured in milliseconds.    -   32 Bits—Packets Sent. This indicates the number of packets that        were sent in the last time interval.    -   32 Bits—Packets Received. This indicates the number of packets        that were received in the last time interval.    -   32 Bits—Packets Resent. This indicates the number of packets        that needed to be resent in the last time interval.    -   16 Bits—Window Size. This value indicates the current window        size that one end is operating under. This will allow for a        random sampling of window sizes to be gathered at the other end.    -   16 Bits—Packets in Flight. This value indicates the current        number of packets that one end has sent to the other end without        receiving an acknowledgement. This will allow for a random        sampling of packets in flight to be gathered by the other end.    -   32 Bits—Time Interval. The span of time that the information in        the QOS packet is dealing with. This parameter is measured in        seconds.

In this manner, both front-end 201 and back-end 203 are aware of notonly their own QoS metrics, but also those of the machine with whichthey are communicating and their shared communication link.

As suggested in FIG. 7, QoS information 708 and time synchronizationinformation 707 can be used by blender 404 to select the order in whichdata is placed into TMP data units 705. Also, QoS information 708 can beused by TMP units 405 and 505 to alter the TMP behavior.

In contrast with conventional TCP mechanisms, the behavior implementedby TMP unit 405 is constantly changing. Because TMP obtains bandwidth tohost a variable number of TCP connections and because TMP is responsiveto information about the variable status of the network, the behavior ofTMP is preferably continuously variable. One of the primary functions ofTMP is being able to act as a conduit for multiple TCP connections. Assuch, a single TMP connection cannot behave in the same manner as asingle TCP connection. For example, imagine that a TMP connection iscarrying 100 TCP connections. At this time, it loses one packet. TCPwould require that the connection bandwidth be cut in half. This is aperformance reduction on 100 connections instead of just on the one thatlost the packet.

Each TCP connection that is passed through the TMP connection must get afair share of the bandwidth, and should not be easily squeezed out bycompeting users of the available bandwidth. To allow this to happen,every TMP connection becomes more aggressive in claiming bandwidth as itaccelerates. Like TCP, the bandwidth available to a particular TMPconnection is measured by its window size (i.e., the number ofoutstanding TCP packets that have not yet been acknowledged). Bandwidthis increased by increasing the window size, and relinquished by reducingthe window size. Up to protocol specified limits, each time a packet issuccessfully delivered and acknowledged, the window size is increaseduntil the window size reaches a protocol specified maximum. When apacket is dropped (e.g., no acknowledge received or a resend packetresponse is received), the bandwidth is decreased by backing off thewindow size. TMP also ensures that it becomes more and more resistant tobacking off (as compared to TCP) with each new TCP connection that ithosts. Further, a TMP should not go down to a window size of less thanthe number of TCP connections that it is hosting.

In a particular implementation, every time a TCP connection is added to(or removed from) what is being passed through the TMP connection, theTMP connection behavior is altered. It is this adaptation that ensuressuccessful connections using TMP. Through the use of the adaptivealgorithms discussed above, TMP is able to adapt the amount of bandwidththat it uses. When a new TCP connection is added to the TMP connection,the TMP connection becomes more aggressive to accommodate it. When a TCPconnection is removed from the TMP connection, the TMP connectionbecomes less aggressive.

The enhanced link 202 provides improved performance in its environmentas compared to conventional TCP channels, but it is recognized thatenhanced link 202 resides on the Internet in the preferredimplementations. Hence, TMP must live together with many protocols andshare the pipe efficiently in order to allow the other protocols fairaccess to the shared communication bandwidth. Since TMP takes only theamount of bandwidth that is appropriate for the number of TCPconnections that it is hosting (and since it monitors the connection andcontrols the number of packets that it puts on the line), TMP will existcooperatively with TCP traffic. Furthermore, since TMP does a better jobat connection monitoring than TCP, TMP is better suited to throughputand bandwidth management than TCP.

FIG. 8 illustrates an exemplary set of processes 808 implemented bypre-processing units 408 and 508. Some, none, or all processesillustrated in FIG. 8 may be implemented on particular packets asdescribed hereinbefore. Unprocessed payload 801 from a payload portionof a packet are passed to processes 808 that perform encryption,compression, and/or error correction. The actual algorithms used toimplement encryption, compression and/or error correction in anyspecific implementation are a design choice made be to meet the needs ofa particular application. Error correction is preferably forward errorcorrection that adds redundant data to the pre-processed payload so thata recipient can reconstruct the payload portion in the presence of oneor more transmission errors. The amount and format of redundantinformation can be varied dynamically to account for current QoSconditions as reported by, for example, QoS information 708.

FIG. 9 illustrates an exemplary set of processes implemented bypost-processing units 407 and 507. Some, none, or all processesillustrated in FIG. 9 may be implemented on particular packets dependingon the corresponding pre-processing performed on the packets.Pre-processed packets are passed to processes that perform decryption,decompression, and/or error correction decoding. The actual algorithmsused in any specific implementation are determined to complement thepre-processing processes. Error correction operates to detect one ormore transmission errors, determine if the detected errors arecorrectable, and when correctable, reforming the corrected payload.Payload portion 903 is essentially a fully-formed payload portion of,for example, an HTTP packet.

Although the invention has been described and illustrated with a certaindegree of particularity, it is understood that the present disclosurehas been made only by way of example, and that numerous changes in thecombination and arrangement of parts can be resorted to by those skilledin the art without departing from the spirit and scope of the invention,as hereinafter claimed. For example, while devices supporting HTTP datatraffic are used in the examples, the HTTP devices may be replaced oraugmented to support other public and proprietary protocols andlanguages including FTP, NNTP, SMTP, SQL and the like. In suchimplementations the front-end 201 and/or back-end 203 are modified toimplement the desired protocol. Moreover, front-end 201 and back-end 203may support different protocols and languages such that the front-end201 supports, for example, HTTP traffic with a client and the back-endsupports a DBMS protocol such as SQL. Such implementations not onlyprovide the advantages of the present invention, but also enable aclient to access a rich set of network resources with minimal clientsoftware.

An additional aspect of the invention is the creation and use of one ormore clients enhanced with the functionality of a front-end mechanism,back-end mechanism, or both. These clients are referred to herein asenhanced clients. In one or more embodiments, these clients mayincorporate, implement, or include a front-end and/or back-end mechanismimplemented by the software, hardware, or both of the enhanced client.For example, as will be described further below, a client such asdescribed above may be enhanced by including software, hardware, or bothwhich allows the client to include the functionality of a front-endmechanism. Typically, but not always, a client may be enhanced bysoftware alone. For example, machine readable code configured to providefront-end and/or back-end functionality when executed by an enhancedclient may be provided. The machine readable code may be fixed on atangible medium, such as a hard drive, memory, or other storage device,accessible to an enhanced client.

In this way, a enhanced link may be implemented by cooperative actionsbetween a plurality of enhanced clients, or between one or more enhancedclients and one or more (stand alone) back-ends, front-ends or both.Enhanced clients may create an enhanced link dynamically. For instance,the enhanced link may be created and used only when communicating withparticular services on a corporate or other LAN. In this way, theenhanced clients provide network link acceleration by taking advantageof the enhanced link and TMP protocol as described herein. The linkacceleration is dynamic in that it may be used when desired or requiredand not used otherwise. It is noted that the benefits described herein(including accelerated communication) of the enhanced link and TMPprotocol be used dynamically by an enhanced client.

FIG. 10 illustrates an exemplary network infrastructure having one ormore enhanced clients 1004. As can be seen, the enhanced clients 1004shown include an internal front-end mechanism 1001 which allows aenhanced link 202 to be implemented between the enhanced clients and oneor more back-ends 203. In this manner, the benefits of the enhanced link202 as described above may be utilized directly by clients.

As can be seen, a front end manager 207 may communicate with an internalfront-end 1001 of the enhanced clients 1004 to provide administrativeand configuration information to front-ends 201. In this manner, theadministration and configuration of the enhanced clients 1004 may beperformed similar to that of stand alone front-ends, such as thosedescribed above with regard to FIG. 2. In fact it is contemplated that afront end manager 207 may provide administrative and configurationinformation to enhanced clients 1004 and stand alone front-endmechanisms.

Elements of an exemplary enhanced client 1004 having a processor 1008and a memory device 1012 will now be described with regard to FIG. 11.It will be understood that the enhanced client 1004 may my configured inother ways and may include additional components as well. For example,the enhanced client 1004 may comprise one or more processors, memorydevices, displays, input devices, output devices, or a combinationthereof.

As can be seen, the enhanced client 1104 includes an internal front-end1001. The internal front-end 1001 may utilize a TCP component 401 of theenhanced client 1104 such as shown. For example, the internal front-end1001 may utilize one or more devices (such as an Ethernet card forexample) and/or software of an enhanced client 1004 for implementing thephysical connection layer and IP layer functionality for TCP. In oneembodiment, the TCP component 401 may be a network stack of the enhancedclient's operating system. Of course, the internal front-end 1001 mayalso or alternatively utilize its own or an internal TCP component 401.It will be understood that where protocols other than TCP/IP aredesired, the TCP component 401 may be replaced or augmented with anappropriate network control process.

As can be seen, the internal front-end 1001 includes similar componentsof a stand alone front-end mechanism. For instance, the internalfront-end may include a parser 402, a data blender 404, a TMP unit 405,a reassemble mechanism 406, a pre-processing mechanism 408, and apost-processing mechanism 407. The internal front-end 1001 may alsooptionally include a caching mechanism 403 such as described above, toimprove performance. In general, like components of the internalfront-end will perform similar or the same function as the componentsdescribed above with regard to the stand alone front-end mechanism.

To illustrate, similar to a stand alone front-end mechanism, thepre-processing mechanism 408 may implement security processes,compression processes, encryption processes, error connection processes,or the like to condition received data for improved performance andfunctionality. The pre-processing mechanism 408 may also prioritizepackets in some embodiments. The data blender 404 may slice and/orcoalesce the data portions of received packets into TMP data units thatare sized for transport through the TMP unit 405. The data blender 404may receive information that enables selection of a preferable TMPpacket size or a fixed TMP packet size that yields desirable performancemay be set. The data blender 404 may mark TMP data units so they can bereassembled when received, serve as a buffer for storing packets, andmay associate a prioritization value with each packet if desired.

Also, similar to the stand alone front-end mechanism, the reassemblemechanism 406 utilizes the data portions of subpackets in TMP packets toreassemble the data portions into a form suitable for return to arequesting client. The postprocessing mechanism 407 may performdecompression, decryption, error correction and the like on packetsreceived from a back-end mechanism. In this manner, the post-processingmechanism 407 restores the data that may have been compressed,encrypted, or the like by a back-end mechanism. In general, thisrestores the data to a usable form or its form before processing by aback-end mechanism.

As stated above, an enhanced client 1004 includes the functionalityand/or components of a front-end mechanism. In one or more embodiments,this may occur by including one or more instructions executable by theenhanced client 1004 to provide the functionality of a front-endmechanism. In one embodiment, this may occur by implementing an internalfront-end 1001 with one or more instructions stored within or otherwiseaccessible by the enhanced client 1004. For example, one or moreinstructions may be stored on a memory device of the enhanced client1004 or hard wired into the circuitry of the enhanced client's hardware.In one embodiment, the one or more instructions may be machine readablecode installed on an enhanced client 1004 or part of an enhancedclient's operating system. It is noted that the one or more instructionsmay be configured to implement one or more or all of the components ofan internal front-end 1001 as described above to provide thefunctionality of a front-end mechanism.

In one embodiment, the one or more instructions are software or driversexecutable by a processor of an enhanced client 1004. The internalfront-end 1001 may be implemented as a network driver or software forcomputer running Windows (trademark of Microsoft Corporation), Linux,UNIX, Macintosh OS, Android (trademark of Google Corporation), iOS(trademark of Apple Corporation), or other operating system. In one ormore embodiments, the internal front-end 1001 may be part of or comewith a default installation of the operating system. Of course, theinternal front end 1001 may be installed or included later as well.

In one or more embodiments, the internal front-end 1001 utilizeshardware of the computer (or other client device) to communicate. Inother words, the internal front-end 1001 allows existing communicationshardware, such as a standard network interface card, to communicate withthe advantages of the enhanced link 202 described herein. Typically,these embodiments of the internal front-end 1001 will by implemented assoftware or machine readable code.

It is noted that in some embodiments, the internal front-end 1001 may beimplemented at least partially by hardware. In one or more embodiments,a hardware add-in card or the like may include devices which arehardwired or configured to execute one or more functions of variouscomponents of an internal front-end. For example, a hardware add-in cardmay comprise one or more ASICs, FPGAs, control logic, and/or firmwarewhich allows one or more functions of the internal front-end 1001 to beperformed by the add-in card.

To illustrate, in one embodiment, the pre-processing and post-processingmechanism may be implemented in hardware to offload processing from aclient's CPU or processor to the internal front-end's hardwarecomponents. In this manner, resource intensive tasks such as encryption,error correction, and the like need not be performed by the processor.Of course, other functions of the internal front-end may be offloaded tohardware as well. In addition, it will be understood that functions maybe shared between the hardware of an internal front-end and a processorof the client.

It is contemplated that the hardware of an internal front-end may beimplemented as an external add-on such as an external device which isconnected to a client by a USB, Bluetooth, or other wired or wirelessinterface/connection. For example, a hardware dongle or the like may beattached to a client when an enhanced link 202 is desired, and detachedwhen not desired. The dongle (or other add-on) may appear to be astandard communications device to the client. In this manner,specialized drivers need not be provided and the add-on may truly beplug-and-play. In operation, the add-on may seamlessly provide theenhanced link 202 between the add-on and a front-end or back-end. Theadd-on may translate packets to/from the enhanced link 202 to a standardprotocol such that the client (and its operating system) may communicatethrough the enhanced link without modification. In some embodiments, theclient may not even know it is communicating through an enhanced link202 due to this translation.

The dongle or add-on may include its own communications devices. Forexample, the add-on may have one or more wired or wireless interfaces toestablish the enhanced link 202 with a back-end or another enhancedclient 1004. It is noted that the add-on may also or alternatively serveas a delivery device for software that provides the front-endcapability. For example, the add-on may comprise a memory device (e.g.,a flash drive or USB drive) that delivers software to a clientautomatically, when connected. The software may also be manuallyaccessed/executed from the add-on.

It will be understood that an enhanced client 1004 may comprise avariety of electronic devices. As stated above, an enhanced client 1004may be a computer or computing device. This includes but is not limitedto personal computers, workstations, and servers. This also includesportable devices such as but not limited to smart phones, laptops,netbooks, tablet PCs.

A client may be enhanced by different methods. For example, in one ormore embodiments, a client may be enhanced through an automated orautomatic process when a user connects to a server, network, or otherdevice which the user wishes to communicate. To illustrate, a client maybe enhanced when its user attempts to or connects with a server or othercomputer within a corporate or other LAN. Once enhanced, the clientwould then be able to communicate with the benefits of the enhanced link202 described herein. As described above, communicating via the enhancedlink 202 is especially advantageous in low bandwidth and/or high latencyconnections which may be common place when a user is physically awayfrom the office or a corporate LAN. For example, a business traveler orhome user may communicate via a enhanced link 202 once his or her clienthas been enhanced. Of course, as stated, the enhanced link 202 isbeneficial in other situations as well.

A LAN network may have many remote clients on many differing types ofWAN links. The services offered to the clients can be delivery of largedocuments, transactional applications such as database access, or simplyweb browsing. Many times these applications on a client are optimizedfor use on the LAN without thought given to possible use across a WAN.These data links may not be well suited for such network servicesbecause of propagation delay inherent by the distance of the connection.They may also be not well suited because of low bandwidth such as wherethe client is connecting through a low bandwidth connection such as DSL,Cable Modem, or even dial-up. Problems with these links can beexacerbated if a VPN connection is used due to the communicationsoverhead resulting from the VPN connection's encryption of data traffic.The links can also be negatively affected by differing MTU sizes thatcan occur during transmission of the packets over the WAN route.

With an enhanced client 1004, a temporary enhanced link 202 may beestablished between the client and a LAN network that offers servicesdesired by the user. When the enhanced client 1004 establishes aconnection to the LAN for the first time, the client may optionallydownload the internal front-end 1001 software. The download action maybe automated so that the user does not even realize that this isoccurring. Alternatively, this action may require user input such as toallow the user to accept or deny installation of the downloaded internalfront-end 1001. It is noted that if the user denies installation, aconnection to the LAN may still be made but without acceleration orother benefits of the enhanced link 202.

If the internal front-end 1001 is installed and the client enhanced,traffic of a first protocol, such as TCP (or another standard protocol)that is targeted to the desired LAN and only traffic targeted to theconnected LAN may be intercepted by the internal front-end 1001 to becommunicated across the enhanced link 202. All other TCP traffic on theclient may continue to be communicated as before without interruption.The traffic that is intercepted may be defined by rules supplied to theenhanced client 1004 by a back-end mechanism or a front-end manager 207in one or more embodiments. For example, a back-end mechanism orfront-end manager 207 may indicate to an enhanced client 1004 thattraffic directed to one or more particular IP addresses, ports, domainnames, or the like be intercepted by the internal front-end so that itmay be communicated through a enhanced link 202 created by cooperativeaction between the internal front-end 1001 and a back-end mechanism.

The back-end mechanism may need to have network access to all thecorporate services that are to be available via the enhanced link 202.After the traffic is intercepted on the enhanced client 1004, it may beconverted into TMP traffic and delivered to the back-end mechanism whereit is converted back to TCP for delivery to the server or other devicehosting the service. Return traffic from the service may also beconverted to TMP traffic for the return trip to the enhanced client 1004via the enhanced link 202. In this manner, the user benefits from theenhanced link 202 created between the internal front-end 1001 of theenhanced client 1004 and the back-end mechanism 203. In addition, thesame benefits of communicating via a stand alone front-end mechanism maybe achieved by direct communication between an enhanced client 1004 andthe back-end mechanism 203.

This is beneficial in that it allows the useful features of the enhancedlink 202 to be extended directly to one or more enhanced clients 1004.For example, accelerated communication, encryption, error correction,quality of service, and security features provided by the enhanced link202 can now be extended to enhanced clients 1004. Thus for example,unlike with standard clients, data may remain encrypted and takeadvantage of error correction and security features of the enhanced link202 until it reaches the enhanced client 1004. Likewise, the data may beencrypted and take advantage of error correction and security featuresas it is sent from an enhanced client 1004.

As stated, the enhanced link 202 between an internal front-end 1001 anda back-end mechanism 203 may be temporary in one or more embodiments. Asdescribed herein, a temporary enhanced link 202 refers to a enhancedlink that is created when a connection to one or more services on a LANare desired by a user, and that is terminated when the services are nolonger needed. For example, a temporary enhanced link 202 may be createdwhen a user desires access to his or her corporate email account andterminated when the user is done accessing his or her email or when theuser logs out of the email account. Also, for example, a temporaryenhanced link 202 may be created when a user requires access to files ordata on a LAN and terminated when the files or data the user desires hasbeen transferred. In one or more embodiments, a temporary enhanced link202 may also or alternatively be terminated after a particular period oftime, when connectivity is lost, when a user shuts down or logs out ofhis or her client device, after a period of inactivity, or if tamperingis detected with the enhanced link's connection. Of course, thetemporary enhanced link 202 may be terminated for other reasons as well.It is contemplated that either the internal front-end 1001, the back-endmechanism, or both may be configured to terminate a enhanced link 202for these and other reasons.

The operation of an internal front-end in connection with an operatingsystem will now be described with regard to FIG. 12. FIG. 12 is a blockdiagram illustrating the interaction between the internal front-end andan operating system. As will be described further below, the internalfront-end's components may be implemented in a front-end process 1216,redirector driver 1224, network stack 1220, or a combination thereof inone or more embodiments. For example, in one or more embodiments, thefront-end process 1216 and redirector driver 1224 may comprise variouscomponents of the internal front-end, as described above.

It is noted that the operating system shown is one of the Windows familyof operating systems. It will be understood that the software mayinteract with other operating systems. For example, software mayinteract with driver interfaces, network stacks, or communicationslayers of other operating systems in the manner described below withregard to the Windows operating system.

As shown by FIG. 12, the enhanced client 1004 has an application space1204 and a kernel space 1208. In general, applications (i.e. software orprograms) run within the application space 1204 supported by servicesprovided by the kernel space 1208. In the figure, a web browserapplication 1212 and a front-end process 1216 are shown running in theapplication space 1204. Of course, other applications may also run inthe application space 1204. A network stack 1220 may be provided in thekernel space 1208. The network stack 1220 may be configured to providecommunication services via TCP/IP or other transport providers (e.g.protocols) through one or more network interface cards or the like. Asshown for example, the network stack 1220 includes Appletalk (Trademarkof Apple Corporation), NetBT, Nbf, and NWlink as transport providers.Applications running on the operating system may utilize thecommunications services of the kernel space 1208 to communicate via thetransport providers shown. Of course, the kernel space 1208 may provideservices for communicating via various transport providers in one ormore embodiments.

As can be seen, a web browser application 1212 or other applications maycommunicate with one or more servers 210 or other devices via a socketinterface and TDI (transport driver interface) client of the networkstack 1220. This includes standard HTTP traffic over TCP/IP. As shownfor example, the web browser application 1212 may communicate through astandard TCP/IP link 1228 to a web or other server 211 by utilizing thenetwork stack 1220.

The web browser application 1212 may also communicate with one or moreservers 210 or other devices by utilizing the front-end process 1216.This allows communication over a enhanced link 202 between the enhancedclient 1004 and back-end mechanism 203 or server. As described above andillustrated in FIG. 12, the enhanced link 202 may be used to accessservices provided by a server 210 through the back-end mechanism 203 inthis manner.

The front-end process 1216 may be machine readable code configured toallow creation and use of an enhanced link 202 for communication. Forexample, the front-end service software 1216 may be an application,process, library (such as a DLL), the like, or a combination thereof. Inone or more embodiments, the front-end process 1216 provides thefunctionality of the internal front-end discussed above. This may beaccomplished by implementing one or more or all the components of theinternal front-end in the front-end process 1216. So configured, thefront-end process 1216 may convert data or packets into TMP packets andvice versa. In addition, the front-end process 1216 may provideencryption, error correction, accelerated communication, and cachingservices as described above. This increases the security, robustness,and speed of network communications. It is noted that the front-endprocess 1216 or a portion thereof may execute within the kernel space1208 in some embodiments. For example, the front-end process 1216 or aportion thereof may be implemented in a TDI (transport driver interface)driver or the like running within the kernel space 1208.

The front-end process 1216 may work in cooperation with a redirectordriver 1224 to receive, convert, and send TMP packets. The redirectordriver 1224 may be configured to intercept and redirect packets to thefront-end process 1216 for conversion to TMP packets that may becommunicated across a enhanced link 202. In addition, the redirectordriver 1224 may convert TMP packets into TCP packets and direct the TCPpackets to an application, such as the web browser application 1212. Inthis manner, an application need not be specially configured tocommunicate through a enhanced link 202 because the front-end process1216 and redirector driver 1224 provide packets usable by theapplication and convert packets from the application into TMP packets.It is contemplated that the redirector driver 1224 may includefunctionality or components of an internal front-end in one or moreembodiments. For example, pre-processing, post-processing, caching orother services of an internal front-end may be provided by theredirector driver 1224. In one or more embodiments, the redirectordriver 1224 may be executed within the kernel space 1208.

In operation, a packet or data may be intercepted by the redirectordriver 1224 when it reaches the network stack 1220 from an application.The redirector driver 1224 may pass the packet to the front-end process1216 which converts the packet into a TMP packet. The converted packetmay then be returned to the network stack 1220 where it may be sent viaa enhanced link 202 to a back-end mechanism 203, such as through anetwork interface card of the enhanced client 1004. A TMP packetreceived from the back-end mechanism 203 via the enhanced link 202 maybe received by the network stack 1220 and redirected by the redirectordriver 1224 to the front-end process 1216 for conversion back to itsoriginal state. Once converted, the packet may pass through the networkstack 1220 to the application it is being sent to (e.g. the applicationwhich requested the packet).

The type of enhanced client and/or its operating system may determinehow the data traffic may be intercepted by the redirector driver 1224.For example, if the enhanced client is running Windows XP then thetraffic may be intercepted at the TDI NDIS (Transport DriverInterface/Network Driver Interface Specification) layer, while onWindows Vista this would be handled at the WFP (Windows FilteringPlatform) layer.

In one or more embodiments, the redirector driver 1224 may be configuredto determine which packets to intercept and redirect based on one ormore routing rules. For example, data from an application in theapplication space 1204 may be passed to the network stack 1220. If anattribute of the packet, such as its destination address or port,matches one or more of the rules, the packet may be intercepted andredirected so that it may be sent in an accelerated fashion over aenhanced link 202. In one or more embodiments, the redirector driver1224 may be configured to examine packets or data received by thenetwork stack and compare one or more attributes (e.g. destinationaddress or port) to one or more routing rules to determine whether thepackets or data should be intercepted and redirected.

It is noted that the routing rules may define various matchingattributes in addition to address and/or port matching. For example, amatching attribute may be the type of protocol used by a packet, qualityof service requirements for a packet, the size of the packet, or thetype of information contained in the packet. In one or more embodiments,the routing rules may define matching attributes comprising one or moreparticular applications. In this manner, traffic to and/or from aparticular application may be intercepted and redirected. For example,the matching attributes may comprise a process ID or process nameindicating the source (or destination) of the packet.

Also or alternatively, the rules may define the IP address of allservices to be accelerated and/or one or more ports to be acceleratedover a enhanced link 202. For example, if a web application usesdatabase transactions or other protocols other than HTTP for deliveringthe web page, these services protocols may be accelerated and optimizedthrough a enhanced link 202 as well.

Routing rules may be provided to an enhanced client in various ways. Forexample, a back-end mechanism 203 may provide one or more rules thatdefine what traffic will be accelerated by a enhanced link 202 betweenthe client laptop and a LAN. In one or more embodiments, the redirectordriver 1224 may be in communication with a back-end mechanism 203 orfront-end manager to receive the rules. In other embodiments, theredirector driver 1224 may receive the rules from the front-end process1216 which may be in communication with the back-end mechanism 203 orfront-end manager. In some embodiments, a user may input one or morerules or the rules may be provided in a data file in the client. Inthese embodiments, the redirector driver 1224 need not receive rulesfrom a source external to the client. The one or more rules may bestored on a memory device of the enhanced client in one or moreembodiments.

It is contemplated that an application may be configured to takeadvantage of an enhanced protocol, such as TMP, and an enhanced link insome embodiments. For example, an internal front-end or front-endprocess may be exposed to application developers via an API. In thismanner, a developer may write applications that utilize the enhancedprotocol and an enhanced link. This is advantageous in that packets orother data may then be directly passed to and from an internal back-endor front-end. Resource utilization may thus be reduced by reducing oreliminating at least some of the processing required to route data to aninternal back-end or front-end. In addition, the number of times datatraverses the network stack may be reduced in this manner.

As stated, the internal front-end may be used to create enhanced clientsfrom standard clients. In one or more embodiments, this may occur byinstalling the internal front-end (including any hardware and/orsoftware of the internal front-end) on the client. An automated installof an internal front-end may occur in some embodiments. For example, inone embodiment, when a client connects to a corporate LAN, the corporateLAN may notify a client that front-end software may be installed foraccelerated/enhanced communication between the client and the corporateLAN. This may occur through a message provided to the user of the clientmachine. Internal front-end software may then be automaticallydownloaded by the client as a result of communication from the corporateLAN. In one embodiment, the corporate LAN or server thereof may cause adownload trigger, such as an “Install” or “Download” button or link tobe presented on the client. The download trigger allows the internalfront-end to be easily downloaded and/or installed on a client. It isnoted that, in some corporate LANs, services provided by the corporateLANs may not be accessible unless the client has or installs a front-endmechanism. Thus, if a user declines installation of the internalfront-end, he or she may be denied access to the corporate LAN. It isnoted that in some embodiments, access to the corporate LAN may bepermitted without installation of the internal front-end, but suchaccess will not take advantage of the benefits provided by an enhancedlink 202 and the TMP protocol.

In an exemplary embodiment, a user may connect to a web site offered bythe corporate LAN over a remote connection, such as a hotel, home, orother public or private access point remote from the corporate LAN. Uponconnecting to the web site with Internet Explorer (trademark ofMicrosoft Corporation) the user may be prompted to allow installation ofan ActiveX (trademark of Microsoft Corporation) component including theinternal front-end. Once installed, the ActiveX component may interceptthe data traffic between the user's client (e.g. laptop or workstationcomputer) and the corporate web server. This traffic may then beaccelerated between the user's machine and the corporate website byconverting the traffic to one or more TMP packets for communicationthrough an enhanced link.

In this example, the corporate web server may provide the ActiveXcontrol and define the parameters of this control, such as by providingthe administrative and configuration services described above withregard to a back-end mechanism or front-end manager. In addition, theweb server may be configured to provide one or more routing rules todefine what traffic is accelerated/enhanced via an enhanced link. Ofcourse, other installation schemes, automated or not, may be utilized toenhance a client. For example, the internal front-end may be provided asan executable file or files which a user may download and install on hisor her client. In some embodiments, the internal front-end may beinstalled and a client enhanced without knowledge of a user. Forexample, a client administrator may cause the internal front-end to beinstalled remotely or the internal front-end may be installed as part ofan automated update to the client's software and/or operating system.

It is noted that an internal front-end of limited functionality may beprovided in one or more embodiments. For example, the internal front-endmay be limited to downloading files or from a server or other source viaan enhanced link. The internal front-end may also be limited todownloading files or other particular data from one or more particularservers. The limited front-end may be provided a reduced or no cost tousers. For example, a website offering large files for download mayprovide the limited internal front-end to increase efficiency and speedof downloads. The internal front-end may be limited in other ways aswell. For example, the internal front-end may be limited to file or datauploads via an enhanced link.

Referring now to FIG. 13, it can be seen that an enhanced client 1004may comprise an internal back-end 1301 in one or more embodiments. Inthis manner, an enhanced client 1004 may establish an enhanced link 202directly with one or more front-ends 201. The enhanced client 1004 mayalso or alternatively establish an enhanced link 202 directly withanother enhanced client, such as an enhanced client comprising aninternal front-end. The internal back-end 1301 may communicate with aback-end manager 209 in some embodiments. For example, administrativeand configuration information for an internal back-end 1301 may bemaintained or updated via a back-end manager 209. Like the internalfront-end, the internal back-end 1301 extends the enhanced link 202directly to the enhanced client 1004. In this way, acceleratedcommunication, encryption, error correction, quality of service, andsecurity features may be extended to the enhanced client 1004.

FIG. 14 shows elements of an exemplary enhanced client 1004 having aninternal back-end 1301. As described above, the enhanced client 1004 maycomprise a processor 1008 and a memory device 1012. The internalback-end 1301 may utilize these (and other) components of the enhancedclient 1004 during operation. For example, the internal back-end 1301may utilize a TCP component 501 of an enhanced client 1004, such as thehardware and/or software stack used to provide TCP functionality at theclient. It is noted that the internal back-end 1301 may include its ownTCP component and may utilize such component (rather than the TCPcomponent of the enhanced client 1004) in some embodiments.

Like the back-end 203 described above, the internal back-end 1301 may beconfigured to translate TMP packets to TCP packets, and vice versa.Accordingly, the internal back-end 1301 may be configured similarly to astand-alone back-end 203. For example, the internal back-end 1301 maycomprise a blender 504, pre-processing mechanism 508, parser 502, TMPunit 505, reassemble mechanism 506, and a post-processing mechanism 507.The internal back-end 1301 may optionally comprise a cache 503 to cachedata packets to improve performance, such as described above.

The components of the internal back-end 1301 may provide the same orsimilar functionality as those found in a stand alone back-end 203. Forexample, the TMP unit 505 may receive TMP packets from an enhanced link202 and pass them to a reassemble mechanism 506, which reassembles thepackets into corresponding TCP packets. The postprocessing mechanism 507may perform decompression, decryption, error correction or the like torestore data processed by and received from a front-end, such asdescribed above with regard to FIG. 11. Likewise, the preprocessingmechanism 508 may perform compression, encryption, error compression andthe like on data to be transmitted by the internal back-end, and forwardsuch data to the data blender 504. As described above, data blender 504may then buffer and prioritize data in a manner efficient fortransmission over the enhanced link. A back-end manager 209 may be usedto maintain or update the manner in which the data blender 504prioritizes data. The data may then be passed to the TCP unit 501 andsubsequently used by the processor 1008 or other component of theenhanced client 1004.

As stated, the internal front-end 1001 may comprise hardware, software,or both that is used to enhance a client. It is contemplated that theinternal back-end 1301 may enhance a client in a similar or the samemanner. For example, like the internal front-end 1001, an internalback-end 1301 may be installed through an automated process, or beimplemented (at least in part) by a hardware add-on or dongle. Also,data may be routed to the internal back-end 1301 or the internalback-end may intercept data based on its source, type (e.g., TMP vs.TCP), or other characteristics. The routing or interception of data maybe defined by rules supplied to the enhanced client 1004, as describedabove. Such rules may be provided by a user directly, through a back-endmanager 209, or through a front-end mechanism (that the internalback-end is communicating with) in some embodiments.

FIG. 15 illustrates operation of an exemplary internal back-end withrespect to an operating system. As can be seen, the internal back-endmay be a back-end process 1304 in the application space 1204 of anoperating system. The back-end process 1304 may utilize a network stack1220 configured to provide communications services to applications inthe application space 1204, such as described above with regard to FIG.12. The back-end process 1304 may work in concert with a redirectordriver 1224 to receive, convert, and send TMP packets, as is alsodescribed above with regard to FIG. 12. For example, the redirectordriver 1224 may receive or intercept TMP packets and pass them to theback-end process 1304 for translation. The translated packets may thenbe sent back through the network stack 1220 to an application, such asthe browser 1212 shown. In addition, TCP packets may be intercepted bythe redirector driver 1224 and passed to the back-end process 1304 forconversion to TMP packets. The TMP packets may then be communicated overthe enhanced link 202. It is contemplated that the TMP packets may alsobe returned to the network stack 1220 and communicated over an enhancedlink 202 by the network stack.

FIG. 16 illustrates an exemplary network environment including enhancedclients 1004. As can be seen, enhanced clients 1004 with internalback-ends 1301 and internal front-ends 1001 may establish andcommunicate directly through an enhanced link 202. As can also be seen,the enhanced clients 1004 may also communicate with stand-alonefront-ends 201 or stand-alone back-ends 203, with their internalback-end 1301 and internal front-end 1001 respectively. An enhancedclient 1004 may utilize these stand-alone front-ends 201 or stand-aloneback-ends 203 to communicate with one or more non-enhanced clients 205or servers 210, such as described above.

As can be seen from FIG. 16, enhanced clients 1004 may optionally haveboth an internal front-end 1001 and an internal back-end 1301. Anenhanced client 1004 with both an internal front-end 1001 and aninternal back-end 1301 may communicate respectively with variousback-ends 201 and various front-ends 203. In addition, such an enhancedclient 1004 may communicate with another enhanced client having only aninternal front-end 1004, only an internal back-end 1301, or having both.

As can be seen, the dynamic network link acceleration method andapparatus herein provides an enhanced link 202 that may be establishedas desired between an enhanced client 1004 and another enhanced client,a front-end mechanism, or a back-end mechanism 203. Where a client doesnot have front-end or back-end services installed, an internal front-endor back-end comprising machine readable instruction code may beautomatically provided/installed or the user may download and installthe software.

The internal front-ends and back-ends described herein may be used toestablish peer to peer networks or links in one or more embodiments. Forexample, two or more enhanced clients may establish a peer to peerconnection through an enhanced link. Packets communicated between theenhanced clients may then be encrypted, prioritized, compressed,accelerated and the like using the TMP protocol. The enhanced clientsmay be portable devices, such as laptops, in one or more embodiments.

It is contemplated that an internal front-end or back-end may includeauto-discovery capabilities in one or more embodiments. For example, aninternal front-end may be able to automatically discover or detect otherfront-end mechanisms, or back-end mechanisms. One or more enhanced linksmay then be established between pairs of front-end and back-endmechanisms. To illustrate, enhanced clients, such as laptops, mayauto-discover one another. Subsequently, one or more enhanced links maybe established (manually or automatically) between the enhanced clients.

The auto-discovery may be used for general networking and communication.Alternatively, the auto-discovery may be used for particularapplications. For example, a meeting or collaboration application mayauto-discover other enhanced clients and include their users in themeeting or collaboration. A peer to peer network including the meetingparticipants may then be established. The participants or users may thenwork together such as by sharing documents, editing documents orwhiteboarding. This is advantageous in that it allows an enhanced linkto be easily setup between enhanced clients. As discussed above, theenhanced link may be used to increase data transfer efficiency, secure,and prioritize data packets between the enhanced clients, among otherthings.

Enhanced clients may also be configured to accelerate data transfers ona per file basis. For example, individual files may have a transparentwrapper or other associated configuration data that defines settings foran enhanced link to accelerate the data transfer. Individual files mayalso be optimized for data transfer.

In addition or alternatively, the internal front-end or back-end may beconfigured to index one or more data files on the enhanced client. Priorto downloading a file (or portions thereof) the enhanced client mayquery the index to determine if parts of the file or the entire file isalready one the enhanced client. Only the portions that are not yet onthe enhanced client may then be downloaded or transmitted. In one ormore embodiments, the data source may send and index of available files,and an enhanced client may select only those files which are not alreadyon the enhanced client for download.

While various embodiments of the invention have been described, it willbe apparent to those of ordinary skill in the art that many moreembodiments and implementations are possible that are within the scopeof this invention. In addition, the various features, elements, andembodiments described herein may be claimed or combined in anycombination or arrangement.

What is claimed is:
 1. An enhanced client computing device comprising:one or more processors configured to process one or more data packets ofa first protocol; at least one front-end configured to: receive the oneor more data packets of the first protocol; encode the one or more datapackets of the first protocol to generate one or more outgoing datapackets of a second protocol, the second protocol being different thanthe first protocol; receive one or more incoming data packets of thesecond protocol transmitted to the enhanced client from a remote device;and decode the one or more incoming data packets to one or more packetsof the first protocol; and at least one network interface configured totransmit the one or more outgoing packets of the second protocol to theremote device over at least one communication channel and receive theone or more incoming data packets of the second protocol transmittedfrom the remote device over the at least one communication channel. 2.The enhanced client in accordance with claim 1 wherein the data packetsof a first protocol are generated by a client application executed bythe one or more processors.
 3. The enhanced client in accordance withclaim 1 wherein the client application comprises a web browser.
 4. Theenhanced client in accordance with claim 1 wherein the at least onefront-end comprises software.
 5. The enhanced client in accordance withclaim 4 where the software is downloaded to a memory of the enhancedclient for execution by the one or more processors.
 6. The enhancedclient in accordance with claim 4 wherein the software comprises anetwork driver.
 7. The enhanced client in accordance with claim 1wherein the front-end is further configured to generate quality ofservice information and transmit the quality of service information tothe remote device.
 8. The enhanced client in accordance with claim 1wherein the quality of service information is associated with one ormore of the outgoing packets of the second protocol.
 9. The enhancedclient in accordance with claim 8 wherein said quality of serviceinformation is located in a header portion of one or more of theoutgoing data packets of the second protocol.
 10. The enhanced client inaccordance with claim 7 wherein said quality of service information istransmitted via data packets of the first protocol.
 11. The enhancedclient in accordance with claim 1 wherein said first protocol comprisesTCP/IP.
 12. The enhanced client in accordance with claim 1 wherein saidremote device comprises a server.
 13. The enhanced client in accordancewith claim 12 wherein said server comprises a web server.
 14. Theenhanced client in accordance with claim 12 wherein said servercomprises a computing device having a back-end, said back-end configuredto: receive the one or more outgoing data packets of the second protocoltransmitted by said enhanced client; decode said received data packetsof the second protocol into received data packets of said firstprotocol; generate said one or more data packets of said second protocolfrom packets of the first protocol; and transmit said one or more datapackets of said second protocol to said enhanced client.
 15. Theenhanced client in accordance with claim 1 wherein said remote devicecomprises another enhanced client.
 16. The enhanced client in accordancewith claim 1 wherein said front-end is configured to intercept said oneor more data packets of said first protocol.
 17. The enhanced client inaccordance with claim 1 wherein said encoding comprises compressing oneor more data packets of the first protocol into one or more data packetsof the second protocol.
 18. The enhanced client in accordance with claim7 wherein said quality of service information comprises time-basedsynchronization information.
 19. The enhanced client in accordance withclaim 12 wherein said server comprises an application which servicesmultiple endpoints.